Skip to content

fix(deps): update dependency webpack-dev-middleware to v5 [security] #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix(deps): update dependency webpack-dev-middleware to v5 [security] #61

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 24, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
webpack-dev-middleware ^3.2.0 → ^5.3.4 age confidence

GitHub Vulnerability Alerts

CVE-2024-29180

Summary

The webpack-dev-middleware middleware does not validate the supplied URL address sufficiently before returning the local file. It is possible to access any file on the developer's machine.

Details

The middleware can either work with the physical filesystem when reading the files or it can use a virtualized in-memory memfs filesystem.
If writeToDisk configuration option is set to true, the physical filesystem is used:
https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/setupOutputFileSystem.js#L21

The getFilenameFromUrl method is used to parse URL and build the local file path.
The public path prefix is stripped from the URL, and the unsecaped path suffix is appended to the outputPath:
https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/getFilenameFromUrl.js#L82
As the URL is not unescaped and normalized automatically before calling the midlleware, it is possible to use %2e and %2f sequences to perform path traversal attack.

PoC

A blank project can be created containing the following configuration file webpack.config.js:
module.exports = { devServer: { devMiddleware: { writeToDisk: true } } };

When started, it is possible to access any local file, e.g. /etc/passwd:
$ curl localhost:8080/public/..%2f..%2f..%2f..%2f../etc/passwd

root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin

Impact

The developers using webpack-dev-server or webpack-dev-middleware are affected by the issue. When the project is started, an attacker might access any file on the developer's machine and exfiltrate the content (e.g. password, configuration files, private source code, ...).

If the development server is listening on a public IP address (or 0.0.0.0), an attacker on the local network can access the local files without any interaction from the victim (direct connection to the port).

If the server allows access from third-party domains (CORS, Allow-Access-Origin: * ), an attacker can send a malicious link to the victim. When visited, the client side script can connect to the local server and exfiltrate the local files.

Recommendation

The URL should be unescaped and normalized before any further processing.

Release Notes

webpack/webpack-dev-middleware (webpack-dev-middleware)

v5.3.4

Compare Source

5.3.4 (2024-03-20)
Bug Fixes

v5.3.3

Compare Source

⚠ BREAKING CHANGES
  • minimum supported webpack version is 5.0.0
  • minimum supported Nodejs version is 14.15.0
5.3.3 (2022-05-18)
Bug Fixes
5.3.2 (2022-05-17)
Bug Fixes
5.3.1 (2022-02-01)
Bug Fixes

v5.3.2

Compare Source

⚠ BREAKING CHANGES
  • minimum supported webpack version is 5.0.0
  • minimum supported Nodejs version is 14.15.0
5.3.3 (2022-05-18)
Bug Fixes
5.3.2 (2022-05-17)
Bug Fixes
5.3.1 (2022-02-01)
Bug Fixes

v5.3.1

Compare Source

⚠ BREAKING CHANGES
  • minimum supported webpack version is 5.0.0
  • minimum supported Nodejs version is 14.15.0
5.3.3 (2022-05-18)
Bug Fixes
5.3.2 (2022-05-17)
Bug Fixes
5.3.1 (2022-02-01)
Bug Fixes

v5.3.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported webpack version is 5.0.0
  • minimum supported Nodejs version is 14.15.0
5.3.3 (2022-05-18)
Bug Fixes
5.3.2 (2022-05-17)
Bug Fixes
5.3.1 (2022-02-01)
Bug Fixes

v5.2.2

Compare Source

Features
5.2.2 (2021-11-17)
Chore
  • update schema-utils package to 4.0.0 version
5.2.1 (2021-09-25)
  • internal release, no visible changes and features

v5.2.1

Compare Source

Features
5.2.2 (2021-11-17)
Chore
  • update schema-utils package to 4.0.0 version
5.2.1 (2021-09-25)
  • internal release, no visible changes and features

v5.2.0

Compare Source

Features
5.2.2 (2021-11-17)
Chore
  • update schema-utils package to 4.0.0 version
5.2.1 (2021-09-25)
  • internal release, no visible changes and features

v5.1.0

Compare Source

Features
  • don't read full file if Range header is present (e8b21f0)
  • output more information on errors (#​1024) (7df9e44)
Bug Fixes

v5.0.0

Compare Source

⚠ BREAKING CHANGES

v4.3.0

Compare Source

Features
Bug Fixes

v4.2.0

Compare Source

Features

v4.1.0

Compare Source

Features
4.0.4 (2021-01-13)
Bug Fixes
4.0.3 (2021-01-12)
Bug Fixes
  • output stats to stdout instead stderr, how does webpack-cli, if you need hide stats from output please use { stats: false } or { stats: 'none' } (4de0f97)
  • colors are working for stats (4de0f97)
  • schema description (#​783) (f9ce2b2)
  • skip Content-type header on unknown types (#​809) (5c9eee5)
4.0.2 (2020-11-10)
Bug Fixes
4.0.1 (2020-11-09)
Bug Fixes
  • compatibility with connect (b83a1db)

v4.0.4

Compare Source

Features
4.0.4 (2021-01-13)
Bug Fixes
4.0.3 (2021-01-12)
Bug Fixes
  • output stats to stdout instead stderr, how does webpack-cli, if you need hide stats from output please use { stats: false } or { stats: 'none' } (4de0f97)
  • colors are working for stats (4de0f97)
  • schema description (#​783) (f9ce2b2)
  • skip Content-type header on unknown types (#​809) (5c9eee5)
4.0.2 (2020-11-10)
Bug Fixes
4.0.1 (2020-11-09)
Bug Fixes
  • compatibility with connect (b83a1db)

v4.0.3

Compare Source

Features
4.0.4 (2021-01-13)
Bug Fixes
4.0.3 (2021-01-12)
Bug Fixes
  • output stats to stdout instead stderr, how does webpack-cli, if you need hide stats from output please use { stats: false } or { stats: 'none' } (4de0f97)
  • colors are working for stats (4de0f97)
  • schema description (#​783) (f9ce2b2)
  • skip Content-type header on unknown types (#​809) (5c9eee5)
4.0.2 (2020-11-10)
Bug Fixes
4.0.1 (2020-11-09)
Bug Fixes
  • compatibility with connect (b83a1db)

v4.0.2

Compare Source

Features
4.0.4 (2021-01-13)
Bug Fixes
4.0.3 (2021-01-12)
Bug Fixes
  • output stats to stdout instead stderr, how does webpack-cli, if you need hide stats from output please use { stats: false } or { stats: 'none' } (4de0f97)
  • colors are working for stats (4de0f97)
  • schema description (#​783) (f9ce2b2)
  • skip Content-type header on unknown types (#​809) (5c9eee5)
4.0.2 (2020-11-10)
Bug Fixes
4.0.1 (2020-11-09)
Bug Fixes
  • compatibility with connect (b83a1db)

v4.0.1

Compare Source

Features
4.0.4 (2021-01-13)
Bug Fixes
4.0.3 (2021-01-12)
Bug Fixes
  • output stats to stdout instead stderr, how does webpack-cli, if you need hide stats from output please use { stats: false } or { stats: 'none' } (4de0f97)
  • colors are working for stats (4de0f97)
  • schema description (#​783) (f9ce2b2)
  • skip Content-type header on unknown types (#​809) (5c9eee5)
4.0.2 (2020-11-10)
Bug Fixes
4.0.1 (2020-11-09)
Bug Fixes
  • compatibility with connect (b83a1db)

v4.0.0

Compare Source

Features
4.0.4 (2021-01-13)
Bug Fixes
4.0.3 (2021-01-12)
Bug Fixes
  • output stats to stdout instead stderr, how does webpack-cli, if you need hide stats from output please use { stats: false } or { stats: 'none' } (4de0f97)
  • colors are working for stats (4de0f97)
  • schema description (#​783) (f9ce2b2)
  • skip Content-type header on unknown types (#​809) (5c9eee5)
4.0.2 (2020-11-10)
Bug Fixes
4.0.1 (2020-11-09)
Bug Fixes
  • compatibility with connect (b83a1db)

v3.7.3

Compare Source

3.7.3 (2020-12-15)
Bug Fixes

v3.7.2

Compare Source

Bug Fixes
4.0.0-rc.0 (2020-02-19)
Bug Fixes
  • respect output.path and output.publicPath options from the configuration
  • respect the stats option from the configuration
  • respect the watchOptions option from the configuration
  • the writeToDisk option now correctly works in multi-compiler mode
  • the outputFileSystem option now correctly works in multi-compiler mode
  • respect [hash]/[fullhash] in output.path and output.publicPath
  • handle exceptions for filesystem operations
  • the Content-Type header doesn't have charset=utf-8 value for custom MIME types and MIME types which can be non utf-8
Features
  • validate options
  • migrate on the webpack logger
  • migrate on the memfs package
  • improve performance
BREAKING CHANGES
  • minimum supported Node.js version is 10.13.0
  • the default value of the option publicPath is taken from the value of the output.publicPath option from the configuration (webpack.config.js)
  • the stats option was removed, the default value of the stats option is taken from the value of the stats option from the configuration (webpack.config.js)
  • the watchOptions was removed, the default value of the watchOptions option is taken from the value of the watchOptions option from the configuration (webpack.config.js)
  • the Content-Type header doesn't have charset=utf-8 value for custom MIME types and MIME types which can be non utf-8
  • the fs option was renamed to the outputFileSystem option
  • the lazy option was removed without replacement
  • the logger, logLevel and logTime options were removed without replacement. You can setup the level value using { infrastructureLogging: { level: 'warn' } }, please read https://webpack.js.org/configuration/other-options/#infrastructurelogging. You can use the infrastructurelog (infrastructureLog in webpack@5) hook to customize logs. The log property in the middleware context was renamed to logger
  • the mimeTypes option first requires you to specify an extension and then a content-type - { mimeTypes: { phtml: 'text/html' } }
  • the force option from the mimeTypes option was removed without replacement
  • the reporter option was removed without replacement
  • the getFilenameFromUrl method was removed from the API
  • the middleware locals now under res.locals.webpack - use res.locals.webpack.stats for access stats and res.locals.webpack.outputFileSystem to access outputFileSystem
3.7.2 (2019-09-28)
Bug Fixes
3.7.1 (2019-09-03)
Bug Fixes

v3.7.1

Compare Source

Bug Fixes
4.0.0-rc.0 (2020-02-19)
Bug Fixes
  • respect output.path and output.publicPath options from the configuration
  • respect the stats option from the configuration
  • respect the watchOptions option from the configuration
  • the writeToDisk option now correctly works in multi-compiler mode
  • the outputFileSystem option now correctly works in multi-compiler mode
  • respect [hash]/[fullhash] in output.path and output.publicPath
  • handle exceptions for filesystem operations
  • the Content-Type header doesn't have charset=utf-8 value for custom MIME types and MIME types which can be non utf-8
Features
  • validate options
  • migrate on the webpack logger
  • migrate on the memfs package
  • improve performance
BREAKING CHANGES
  • minimum supported Node.js version is 10.13.0
  • the default value of the option publicPath is taken from the value of the output.publicPath option from the configuration (webpack.config.js)
  • the stats option was removed, the default value of the stats option is taken from the value of the stats option from the configuration (webpack.config.js)
  • the watchOptions was removed, the default value of the watchOptions option is taken from the value of the watchOptions option from the configuration (webpack.config.js)
  • the Content-Type header doesn't have charset=utf-8 value for custom MIME types and MIME types which can be non utf-8
  • the fs option was renamed to the outputFileSystem option
  • the lazy option was removed without replacement
  • the logger, logLevel and logTime options were removed without replacement. You can setup the level value using { infrastructureLogging: { level: 'warn' } }, please read https://webpack.js.org/configuration/other-options/#infrastructurelogging. You can use the infrastructurelog (infrastructureLog in webpack@5) hook to customize logs. The log property in the middleware context was renamed to logger
  • the mimeTypes option first requires you to specify an extension and then a content-type - { mimeTypes: { phtml: 'text/html' } }
  • the force option from the mimeTypes option was removed without replacement
  • the reporter option was removed without replacement
  • the getFilenameFromUrl method was removed from the API
  • the middleware locals now under res.locals.webpack - use res.locals.webpack.stats for access stats and res.locals.webpack.outputFileSystem to access outputFileSystem
3.7.2 (2019-09-28)
Bug Fixes
3.7.1 (2019-09-03)
Bug Fixes

v3.7.0

Compare Source

Bug Fixes
4.0.0-rc.0 (2020-02-19)
Bug Fixes
  • respect output.path and output.publicPath options from the configuration
  • respect the stats option from the configuration
  • respect the watchOptions option from the configuration
  • the writeToDisk option now correctly works in multi-compiler mode
  • the outputFileSystem option now correctly works in multi-compiler mode
  • respect [hash]/[fullhash] in output.path and output.publicPath
  • handle exceptions for filesystem operations
  • the Content-Type header doesn't have charset=utf-8 value for custom MIME types and MIME types which can be non utf-8
Features
  • validate options
  • migrate on the webpack logger
  • migrate on the memfs package
  • improve performance
BREAKING CHANGES
  • minimum supported Node.js version is 10.13.0
  • the default value of the option publicPath is taken from the value of the output.publicPath option from the configuration (webpack.config.js)
  • the stats option was removed, the default value of the stats option is taken from the value of the stats option from the configuration (webpack.config.js)
  • the watchOptions was removed, the default value of the watchOptions option is taken from the value of the watchOptions option from the configuration (webpack.config.js)
  • the Content-Type header doesn't have charset=utf-8 value for custom MIME types and MIME types which can be non utf-8
  • the fs option was renamed to the outputFileSystem option
  • the lazy option was removed without replacement
  • the logger, logLevel and logTime options were removed without replacement. You can setup the level value using { infrastructureLogging: { level: 'warn' } }, please read https://webpack.js.org/configuration/other-options/#infrastructurelogging. You can use the infrastructurelog (infrastructureLog in webpack@5) hook to customize logs. The log property in the middleware context was renamed to logger
  • the mimeTypes option first requires you to specify an extension and then a content-type - { mimeTypes: { phtml: 'text/html' } }
  • the force option from the mimeTypes option was removed without replacement
  • the reporter option was removed without replacement
  • the getFilenameFromUrl method was removed from the API
  • the middleware locals now under res.locals.webpack - use res.locals.webpack.stats for access stats and res.locals.webpack.outputFileSystem to access outputFileSystem
3.7.2 (2019-09-28)
Bug Fixes
3.7.1 (2019-09-03)
Bug Fixes

v3.6.2

Compare Source

Bug Fixes
  • check existence of res.getHeader and set the correct Content-Type (#​385) (56dc705)

v3.6.1

Compare Source

Bug Fixes
  • do not overwrite Content-Type if header already exists (#​377) (b2a6fed)

v3.6.0

Compare Source

Features

v3.5.2

Compare Source

Bug Fixes

v3.5.1

Compare Source

Bug Fixes
  • remove querystring from filenames when writing to disk (#​361) (90d0d94)

v3.5.0

Compare Source

Bug Fixes
Features
  • allow to redefine mimeTypes (possible to use force option) (#​349) (e56a181)

v3.4.0

Compare Source

Bug Fixes
  • index: don't modify the default behavior for unhandledRejection (#​340) (f0a8e3e)
  • middleware: replace url-join with path.posix.join (#​334) (d75802b)

v3.3.0

Compare Source

Features
  • middleware: expose the memory filesystem (response.locals.fs) (#​337) (f9a138e)

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 3a2b362 to f1ff602 Compare March 24, 2024 14:55
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] Mar 24, 2024
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] Mar 24, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from f1ff602 to 5b38b7d Compare March 24, 2024 16:43
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 5b38b7d to 8a8de5b Compare April 14, 2024 09:18
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] Apr 14, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 8a8de5b to 22f6c75 Compare April 14, 2024 13:46
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] Apr 14, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 22f6c75 to d573cbf Compare April 21, 2024 08:20
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] Apr 21, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from d573cbf to b0b3cb8 Compare April 21, 2024 09:09
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] Apr 21, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from b0b3cb8 to 15e303e Compare April 25, 2024 09:00
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] Apr 25, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 15e303e to 0177ef4 Compare April 25, 2024 12:52
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] Apr 25, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 0177ef4 to 419970a Compare May 1, 2024 09:20
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] May 1, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 419970a to bfa6fa1 Compare May 1, 2024 13:20
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] May 1, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from bfa6fa1 to 09172b5 Compare May 9, 2024 12:08
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] May 9, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 09172b5 to bf9a1c9 Compare May 9, 2024 17:18
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] May 9, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from bf9a1c9 to 5d7411e Compare May 15, 2024 19:00
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] May 15, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 5d7411e to 1371663 Compare May 16, 2024 02:18
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] May 16, 2024
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 1371663 to cba0a64 Compare June 4, 2024 10:16
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] Jun 4, 2024
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] Sep 25, 2025
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 812b264 to fd4faae Compare October 21, 2025 21:57
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] Oct 21, 2025
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from fd4faae to fcc8c19 Compare October 22, 2025 09:47
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] Oct 22, 2025
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from fcc8c19 to 3d8422d Compare November 10, 2025 17:40
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] Nov 10, 2025
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 3d8422d to ada273a Compare November 11, 2025 03:50
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] Nov 11, 2025
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from ada273a to 01b659f Compare November 18, 2025 15:01
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] Nov 18, 2025
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 01b659f to 923a064 Compare November 19, 2025 01:29
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] Nov 19, 2025
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 923a064 to 8f235a8 Compare December 3, 2025 20:04
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] Dec 3, 2025
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 8f235a8 to 78ffa89 Compare December 3, 2025 21:28
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] Dec 3, 2025
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 78ffa89 to 576a4b7 Compare December 30, 2025 12:44
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] Dec 30, 2025
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 576a4b7 to dca44e4 Compare December 30, 2025 17:59
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] Dec 30, 2025
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] Dec 31, 2025
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch 2 times, most recently from 5d1dc4d to 62cadf9 Compare December 31, 2025 22:32
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] Dec 31, 2025
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from 62cadf9 to de75266 Compare January 8, 2026 20:37
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v5 [security] fix(deps): update dependency webpack-dev-middleware to v7 [security] Jan 8, 2026
@renovate renovate bot force-pushed the renovate/npm-webpack-dev-middleware-vulnerability branch from de75266 to 3cc78f5 Compare January 9, 2026 01:04
@renovate renovate bot changed the title fix(deps): update dependency webpack-dev-middleware to v7 [security] fix(deps): update dependency webpack-dev-middleware to v5 [security] Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant